Summary

• wire Odoo profiles into the generic-web post-deploy extension hook for generic deploy and rollback apply
• carry generic rollback post_deploy_status through workflow results and accepted route responses
• document that Odoo still keeps its product-specific rollback route for release tuple and promotion-state bookkeeping

Validation

• uv run python -m unittest tests.test_service tests.test_generic_web_deploy tests.test_generic_web_rollback
• uv run --extra dev ruff check --diff control_plane/service.py control_plane/workflows/generic_web_rollback.py tests/test_service.py
• uv run --extra dev ruff check control_plane/service.py control_plane/workflows/generic_web_rollback.py tests/test_service.py
• uv run --extra dev ruff format --check control_plane/service.py control_plane/workflows/generic_web_rollback.py tests/test_service.py
• uv run --extra dev mypy control_plane tests
• uv run python -m unittest
• uv run /Users/cbusillo/Developer/codex-skills/jetbrains-inspection/scripts/jb-inspect.py run --repo "$PWD" --scope changed_files